Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b1b4df1e9fc7cdcb87f7f53d3ff4faeb31277876aa7d3828167dbd69d4d049d

Tx prefix hash: e7a864a4aa03147408daa6995bdd655bbd4841d501198b52514c17404d234683
Tx public key: 14e086e1299224fac9f2361cc23d4dde572657f7cb9ac229163a4fd7dad7e415
Timestamp: 1728661941 Timestamp [UCT]: 2024-10-11 15:52:21 Age [y:d:h:m:s]: 00:174:07:41:59
Block: 1129361 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124379 RingCT/type: yes/0
Extra: 0114e086e1299224fac9f2361cc23d4dde572657f7cb9ac229163a4fd7dad7e415021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0d5add83b3e44351c683461f1a16d3fa0c3dd0d6fcde65a5ab8e4d9720535d5 0.600000000000 1612186 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": 1129371, "vin": [ { "gen": { "height": 1129361 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0d5add83b3e44351c683461f1a16d3fa0c3dd0d6fcde65a5ab8e4d9720535d5" } } ], "extra": [ 1, 20, 224, 134, 225, 41, 146, 36, 250, 201, 242, 54, 28, 194, 61, 77, 222, 87, 38, 87, 247, 203, 154, 194, 41, 22, 58, 79, 215, 218, 215, 228, 21, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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