Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb90cc04223df2eeff717bc77cfb92f6886091de7cf5aa97034cebbcd48407e7

Tx prefix hash: dbf674f267c1692f516d119df80bf2fb4ff108af07f6f19d8de8117a029a6b2a
Tx public key: 404e798285d6ea48104794d25ae9be318cc2e7ab57e64b3433fb2d87de76d166
Timestamp: 1729886724 Timestamp [UCT]: 2024-10-25 20:05:24 Age [y:d:h:m:s]: 00:163:21:11:15
Block: 1139488 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116912 RingCT/type: yes/0
Extra: 01404e798285d6ea48104794d25ae9be318cc2e7ab57e64b3433fb2d87de76d1660211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5e81fd2458bdb760911c1a902ad299478a2449e4cea82c4a9fa5aaa202d2bfd3 0.600000000000 1623275 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": 1139498, "vin": [ { "gen": { "height": 1139488 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5e81fd2458bdb760911c1a902ad299478a2449e4cea82c4a9fa5aaa202d2bfd3" } } ], "extra": [ 1, 64, 78, 121, 130, 133, 214, 234, 72, 16, 71, 148, 210, 90, 233, 190, 49, 140, 194, 231, 171, 87, 230, 75, 52, 51, 251, 45, 135, 222, 118, 209, 102, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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