Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fdd2db829696369773bdfb089099966b63f7f5f9c24bba16df19f7b847accca3

Tx prefix hash: cd8cd1b3bf7af078e6670743ab24936129a4931b3e7b3d5a3b3bcd0e5c2e1688
Tx public key: 131927ec6084a279c4f0779520d0a21c717fa6ef95f8d5fb6d71e3f60594e44e
Timestamp: 1737048917 Timestamp [UCT]: 2025-01-16 17:35:17 Age [y:d:h:m:s]: 00:059:17:37:09
Block: 1198752 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 42482 RingCT/type: yes/0
Extra: 01131927ec6084a279c4f0779520d0a21c717fa6ef95f8d5fb6d71e3f60594e44e021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 07cbc60c83e451e11be35ecebdf533d93fa21a1068ede88c13dc2560830385f8 0.600000000000 1685379 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": 1198762, "vin": [ { "gen": { "height": 1198752 } } ], "vout": [ { "amount": 600000000, "target": { "key": "07cbc60c83e451e11be35ecebdf533d93fa21a1068ede88c13dc2560830385f8" } } ], "extra": [ 1, 19, 25, 39, 236, 96, 132, 162, 121, 196, 240, 119, 149, 32, 208, 162, 28, 113, 127, 166, 239, 149, 248, 213, 251, 109, 113, 227, 246, 5, 148, 228, 78, 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