Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17a378536324bfc91dc4233b8f5c69c2971296f152775cc6140a67f6ad5de834

Tx prefix hash: 3eb0f79adeb0ebd837737db9cd4bc546d864fe1fbc0e6bffe2e0569b0f5b4ca3
Tx public key: b9e284e2ddb5f5563b03f2c0174aac7050e521eccde9365c0b70877d55c52c5f
Timestamp: 1706194746 Timestamp [UCT]: 2024-01-25 14:59:06 Age [y:d:h:m:s]: 01:142:14:52:55
Block: 943072 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 362977 RingCT/type: yes/0
Extra: 01b9e284e2ddb5f5563b03f2c0174aac7050e521eccde9365c0b70877d55c52c5f02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e7984a2809cf01041ca590658ab0b6608a192b0fc33f4b626d261dd2a302493d 0.600000000000 1401270 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": 943082, "vin": [ { "gen": { "height": 943072 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e7984a2809cf01041ca590658ab0b6608a192b0fc33f4b626d261dd2a302493d" } } ], "extra": [ 1, 185, 226, 132, 226, 221, 181, 245, 86, 59, 3, 242, 192, 23, 74, 172, 112, 80, 229, 33, 236, 205, 233, 54, 92, 11, 112, 135, 125, 85, 197, 44, 95, 2, 17, 0, 0, 0, 1, 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