Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c340351510cc506f8c01bddb37a290a36d0161c978f352ee7098b17bb938356

Tx prefix hash: 77074ef72797401a5a8a1e41890f14ff112b2b5a95bf58c1033ebb4d47fd5999
Tx public key: 2c2648a4c629aa2ec0e7596046ed92fe284f4ac6e7986dbc2d188deb05f8dd5b
Timestamp: 1735341425 Timestamp [UCT]: 2024-12-27 23:17:05 Age [y:d:h:m:s]: 00:172:16:48:19
Block: 1184608 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123153 RingCT/type: yes/0
Extra: 012c2648a4c629aa2ec0e7596046ed92fe284f4ac6e7986dbc2d188deb05f8dd5b021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9553376fc1fab31cb59f95db1e22667fa4be08312b37d8ec967eb12e71e5e862 0.600000000000 1671067 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": 1184618, "vin": [ { "gen": { "height": 1184608 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9553376fc1fab31cb59f95db1e22667fa4be08312b37d8ec967eb12e71e5e862" } } ], "extra": [ 1, 44, 38, 72, 164, 198, 41, 170, 46, 192, 231, 89, 96, 70, 237, 146, 254, 40, 79, 74, 198, 231, 152, 109, 188, 45, 24, 141, 235, 5, 248, 221, 91, 2, 17, 0, 0, 0, 3, 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