Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cbcd3bfa792177605bf652e80b271db874127120e83a18fbebe69981ff78857a

Tx prefix hash: 838fa8874f079d04fef70614a564fd128e3a62cd4a594cb405ce9b4ad797b8bf
Tx public key: de5c3c7f3f9139648716dec9662af534d7809cab3b7fb19879c33829b1a6e61a
Timestamp: 1713164027 Timestamp [UCT]: 2024-04-15 06:53:47 Age [y:d:h:m:s]: 00:223:12:50:16
Block: 1000872 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160034 RingCT/type: yes/0
Extra: 01de5c3c7f3f9139648716dec9662af534d7809cab3b7fb19879c33829b1a6e61a0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1cb79c981ec6584b5868bc7d7bfd3f1e0b918a14f9f21d4d4b3395635705b902 0.600000000000 1461372 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": 1000882, "vin": [ { "gen": { "height": 1000872 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1cb79c981ec6584b5868bc7d7bfd3f1e0b918a14f9f21d4d4b3395635705b902" } } ], "extra": [ 1, 222, 92, 60, 127, 63, 145, 57, 100, 135, 22, 222, 201, 102, 42, 245, 52, 215, 128, 156, 171, 59, 127, 177, 152, 121, 195, 56, 41, 177, 166, 230, 26, 2, 17, 0, 0, 0, 4, 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