Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f627e3edf5a09358317e7e1052a5a8895569ebb57ae668eca09fea0e0fbef02d

Tx prefix hash: 7596114ecb2861448cad38c5c8b8d2a982af97011e3a7b92a70557440d567ed2
Tx public key: a2d9dc357d5a015e8bfb600c4b647ee5c5954ce04b73da98faf7ce38ad297b26
Timestamp: 1713757477 Timestamp [UCT]: 2024-04-22 03:44:37 Age [y:d:h:m:s]: 00:186:12:38:23
Block: 1005798 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133571 RingCT/type: yes/0
Extra: 01a2d9dc357d5a015e8bfb600c4b647ee5c5954ce04b73da98faf7ce38ad297b260211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1d2a51f24d637982262cb1ff3bd9cbe2f5f4ce75264486929bbf6b692de09a2e 0.600000000000 1466604 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": 1005808, "vin": [ { "gen": { "height": 1005798 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1d2a51f24d637982262cb1ff3bd9cbe2f5f4ce75264486929bbf6b692de09a2e" } } ], "extra": [ 1, 162, 217, 220, 53, 125, 90, 1, 94, 139, 251, 96, 12, 75, 100, 126, 229, 197, 149, 76, 224, 75, 115, 218, 152, 250, 247, 206, 56, 173, 41, 123, 38, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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