Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1bb74582c6e016b2dd4688cb4e27decd7c292ce804d3fdd8946479e36e57ec8a

Tx prefix hash: 70d59c3be71130b9d90d7e54e47863b44235ebbe3946a596900698d7ecda4d79
Tx public key: 79dc81b9d52c93e2030b5c83bc2a49e0065aa2c3775000b4f2dedbc58c9fe51a
Timestamp: 1717567442 Timestamp [UCT]: 2024-06-05 06:04:02 Age [y:d:h:m:s]: 01:014:13:30:15
Block: 1037391 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 271183 RingCT/type: yes/0
Extra: 0179dc81b9d52c93e2030b5c83bc2a49e0065aa2c3775000b4f2dedbc58c9fe51a02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 359349f063de06cba4df32a1b63c3f1a3d8948bcd727df396452069a880aa041 0.600000000000 1505922 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": 1037401, "vin": [ { "gen": { "height": 1037391 } } ], "vout": [ { "amount": 600000000, "target": { "key": "359349f063de06cba4df32a1b63c3f1a3d8948bcd727df396452069a880aa041" } } ], "extra": [ 1, 121, 220, 129, 185, 213, 44, 147, 226, 3, 11, 92, 131, 188, 42, 73, 224, 6, 90, 162, 195, 119, 80, 0, 180, 242, 222, 219, 197, 140, 159, 229, 26, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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