Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0da115e53c2bfd46d596a276e08aef76708a68b2d8740915cb687b1e73842f55

Tx prefix hash: 56217ef1a98e3b9291a0f7de27367e7ceab8ce1e1fe27b41ea4e36e77871d9fa
Tx public key: b51028cb950ef6496ef82404553cd546243d9dd49778b21f262fe1368e5b85e2
Timestamp: 1725895021 Timestamp [UCT]: 2024-09-09 15:17:01 Age [y:d:h:m:s]: 00:209:10:24:27
Block: 1106433 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149502 RingCT/type: yes/0
Extra: 01b51028cb950ef6496ef82404553cd546243d9dd49778b21f262fe1368e5b85e202110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 406a24b5b2f8cab5ae17ff59b1afa41a9fec0fa8533ab2ab258e560b993279a7 0.600000000000 1584032 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": 1106443, "vin": [ { "gen": { "height": 1106433 } } ], "vout": [ { "amount": 600000000, "target": { "key": "406a24b5b2f8cab5ae17ff59b1afa41a9fec0fa8533ab2ab258e560b993279a7" } } ], "extra": [ 1, 181, 16, 40, 203, 149, 14, 246, 73, 110, 248, 36, 4, 85, 60, 213, 70, 36, 61, 157, 212, 151, 120, 178, 31, 38, 47, 225, 54, 142, 91, 133, 226, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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