Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f1f014b9de4594631e2913ba7c1b5af55ddd18a882f3f73fc7e6f3438060654

Tx prefix hash: 60ebd761b93df40baee93df7fac7716ed85fded208068987af462e16daf519eb
Tx public key: 50c54cc447c8e68a2abe9175a2b85b2a7e53e65839303e1f5b5e10ca2ff8938b
Timestamp: 1735191361 Timestamp [UCT]: 2024-12-26 05:36:01 Age [y:d:h:m:s]: 00:085:03:09:21
Block: 1183385 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 60631 RingCT/type: yes/0
Extra: 0150c54cc447c8e68a2abe9175a2b85b2a7e53e65839303e1f5b5e10ca2ff8938b021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0eeac38970be32a01b357ba3573cc9e7fc1f9509c57615865c626d5483efcdd3 0.600000000000 1669830 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": 1183395, "vin": [ { "gen": { "height": 1183385 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0eeac38970be32a01b357ba3573cc9e7fc1f9509c57615865c626d5483efcdd3" } } ], "extra": [ 1, 80, 197, 76, 196, 71, 200, 230, 138, 42, 190, 145, 117, 162, 184, 91, 42, 126, 83, 230, 88, 57, 48, 62, 31, 91, 94, 16, 202, 47, 248, 147, 139, 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