Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ca627553dd1911056e4a4633f41d6019a8fbbf4bff0a25ed00b90f6183dc994

Tx prefix hash: aa9707f515585454ddff58fd919a4de6d40481bc1d5c33af5cd7d93da83f8347
Tx public key: e7c474a373beff7654f489b5238d30117ccb319c4eccae060f226a5ac3a0e338
Timestamp: 1702673220 Timestamp [UCT]: 2023-12-15 20:47:00 Age [y:d:h:m:s]: 01:329:01:49:21
Block: 913904 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 494044 RingCT/type: yes/0
Extra: 01e7c474a373beff7654f489b5238d30117ccb319c4eccae060f226a5ac3a0e33802110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b6bafa507e8304331f4daa01a9019c46591cf20f1475e8f2a8e0b84da84a70c2 0.600000000000 1371184 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": 913914, "vin": [ { "gen": { "height": 913904 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6bafa507e8304331f4daa01a9019c46591cf20f1475e8f2a8e0b84da84a70c2" } } ], "extra": [ 1, 231, 196, 116, 163, 115, 190, 255, 118, 84, 244, 137, 181, 35, 141, 48, 17, 124, 203, 49, 156, 78, 204, 174, 6, 15, 34, 106, 90, 195, 160, 227, 56, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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