Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d53c66d1fdf00855cf28397e8973e8af53a75f8c4f065fe10fba7dbfad66052

Tx prefix hash: 2bb88ce90829fcb063e4e75301cf91d6dc81e833010bf6118543ef946e217745
Tx public key: 7b77064f2ca8d901ea74b4224f3e3140d769d2a204ba12f839a636be24f847e0
Timestamp: 1727191311 Timestamp [UCT]: 2024-09-24 15:21:51 Age [y:d:h:m:s]: 00:061:09:07:36
Block: 1117184 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 43861 RingCT/type: yes/0
Extra: 017b77064f2ca8d901ea74b4224f3e3140d769d2a204ba12f839a636be24f847e002110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8955da3f28d07a4165654fe5b7da37c89232cc0aec663cb0285585666dcc6ea9 0.600000000000 1597927 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": 1117194, "vin": [ { "gen": { "height": 1117184 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8955da3f28d07a4165654fe5b7da37c89232cc0aec663cb0285585666dcc6ea9" } } ], "extra": [ 1, 123, 119, 6, 79, 44, 168, 217, 1, 234, 116, 180, 34, 79, 62, 49, 64, 215, 105, 210, 162, 4, 186, 18, 248, 57, 166, 54, 190, 36, 248, 71, 224, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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