Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6382b70669c90fa5855da88ad9b55b3a98cfd0d1c6f64e34c1874d8342d836db

Tx prefix hash: cb665abdd5a1bae16eb831c5828f110fd22e77b854e77a83e62595e6ae747009
Tx public key: d7ea208c89e2a47fe7f6305ddcdc521c47c31fe63a5231efc033b8c64d24fd47
Timestamp: 1718105417 Timestamp [UCT]: 2024-06-11 11:30:17 Age [y:d:h:m:s]: 01:120:02:47:56
Block: 1041858 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344356 RingCT/type: yes/0
Extra: 01d7ea208c89e2a47fe7f6305ddcdc521c47c31fe63a5231efc033b8c64d24fd470211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 43fdadc7dbe34683cbae4c9571c177810dd0e12514bebc1201b42b122b81a327 0.600000000000 1510633 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": 1041868, "vin": [ { "gen": { "height": 1041858 } } ], "vout": [ { "amount": 600000000, "target": { "key": "43fdadc7dbe34683cbae4c9571c177810dd0e12514bebc1201b42b122b81a327" } } ], "extra": [ 1, 215, 234, 32, 140, 137, 226, 164, 127, 231, 246, 48, 93, 220, 220, 82, 28, 71, 195, 31, 230, 58, 82, 49, 239, 192, 51, 184, 198, 77, 36, 253, 71, 2, 17, 0, 0, 0, 3, 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