Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3486f620911fe6063eae301b97e21cccb04a7ca7a5224d1efff6f96595db33f4

Tx prefix hash: 0e08d89841d52a6f6572e4743681bc3d24b49f6a9a4c7edb19518e246acb74d6
Tx public key: 6d92453c85488e8ab452a1c3e3352e7bfcbd5020f8187157504fc3f7c8a1103a
Timestamp: 1713609038 Timestamp [UCT]: 2024-04-20 10:30:38 Age [y:d:h:m:s]: 00:285:19:14:06
Block: 1004555 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204319 RingCT/type: yes/0
Extra: 016d92453c85488e8ab452a1c3e3352e7bfcbd5020f8187157504fc3f7c8a1103a0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 98c7961dc1486b700a4a02503ce6dbfe4a1c439b797b194887276d01ec6fb8e6 0.600000000000 1465123 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": 1004565, "vin": [ { "gen": { "height": 1004555 } } ], "vout": [ { "amount": 600000000, "target": { "key": "98c7961dc1486b700a4a02503ce6dbfe4a1c439b797b194887276d01ec6fb8e6" } } ], "extra": [ 1, 109, 146, 69, 60, 133, 72, 142, 138, 180, 82, 161, 195, 227, 53, 46, 123, 252, 189, 80, 32, 248, 24, 113, 87, 80, 79, 195, 247, 200, 161, 16, 58, 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