Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 588af66bcc5eb193f4cd7e9e06aa423e9a3662ee9b0756299c513181fbfed99f

Tx prefix hash: ddc9ba3b35752a44f242a50c37efcb8db3427e935d08a33a7d05fa38244bd8e7
Tx public key: 863c2ba820cbefb285a1ee908b4fa2fd0ee0f13b24b27eb98cc083a43014b5c8
Timestamp: 1736834934 Timestamp [UCT]: 2025-01-14 06:08:54 Age [y:d:h:m:s]: 00:155:03:08:33
Block: 1196982 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110579 RingCT/type: yes/0
Extra: 01863c2ba820cbefb285a1ee908b4fa2fd0ee0f13b24b27eb98cc083a43014b5c8021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2cb91d6c91eb472aab376ec95e3e72e059132f9db65ac515e5b098fd1780693f 0.600000000000 1683587 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": 1196992, "vin": [ { "gen": { "height": 1196982 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2cb91d6c91eb472aab376ec95e3e72e059132f9db65ac515e5b098fd1780693f" } } ], "extra": [ 1, 134, 60, 43, 168, 32, 203, 239, 178, 133, 161, 238, 144, 139, 79, 162, 253, 14, 224, 241, 59, 36, 178, 126, 185, 140, 192, 131, 164, 48, 20, 181, 200, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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