Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: f3a3df4aae0320f04782584ecdc3177152d630f1c34a01ab532207443b29f904

Tx prefix hash: 264a77f0656fe455c144064e712f0628076ab6e77af8261e0a8ebe5e402f013e
Tx public key: 55b346bee5f250925f05c8b5be15e8084905e7f11f3731816a23838926751717
Timestamp: 1715136388 Timestamp [UCT]: 2024-05-08 02:46:28 Age [y:d:h:m:s]: 00:345:11:44:53
Block: 1017233 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 246969 RingCT/type: yes/0
Extra: 0155b346bee5f250925f05c8b5be15e8084905e7f11f3731816a238389267517170211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a5c78e07d2cf8c88643cbc3b49e051f066df0c6c667dfa613e3a3d51606e99f 0.600000000000 1481002 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1017243, "vin": [ { "gen": { "height": 1017233 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a5c78e07d2cf8c88643cbc3b49e051f066df0c6c667dfa613e3a3d51606e99f" } } ], "extra": [ 1, 85, 179, 70, 190, 229, 242, 80, 146, 95, 5, 200, 181, 190, 21, 232, 8, 73, 5, 231, 241, 31, 55, 49, 129, 106, 35, 131, 137, 38, 117, 23, 23, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8