Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca24b00ca61ea0b3f815629a5f49d18999c6fefe2a05861a380996097e651b62

Tx prefix hash: 6cda2fe98ace9cc6d5f2ca7e842f1f9418494594ac2f37447d8801782f5aca7d
Tx public key: dc4918f72ccba160d17a73e8c1cb22882cfd1515e015e50c00d903484c9f8f5b
Timestamp: 1704495144 Timestamp [UCT]: 2024-01-05 22:52:24 Age [y:d:h:m:s]: 01:161:08:27:45
Block: 929000 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 376389 RingCT/type: yes/0
Extra: 01dc4918f72ccba160d17a73e8c1cb22882cfd1515e015e50c00d903484c9f8f5b02110000000f0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3939f677bb652d3c4c274681d036d62a377727ba0a264bf11f1ca0392c12a862 0.600000000000 1386868 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": 929010, "vin": [ { "gen": { "height": 929000 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3939f677bb652d3c4c274681d036d62a377727ba0a264bf11f1ca0392c12a862" } } ], "extra": [ 1, 220, 73, 24, 247, 44, 203, 161, 96, 209, 122, 115, 232, 193, 203, 34, 136, 44, 253, 21, 21, 224, 21, 229, 12, 0, 217, 3, 72, 76, 159, 143, 91, 2, 17, 0, 0, 0, 15, 0, 17, 5, 91, 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