Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5c51e7b9a251fa3be8289db0e191a292f3d53dd2c027571a296de78fb5bfd68

Tx prefix hash: cd0ddef338982a644a8b738f73a161e4d9d67c0815d43c20456496ce17fa1e62
Tx public key: b2d8a0a5a3da38c299ebf8bac85610cdae6b9536328addd81ca169ff283d7755
Timestamp: 1732185002 Timestamp [UCT]: 2024-11-21 10:30:02 Age [y:d:h:m:s]: 00:002:03:00:24
Block: 1158472 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1525 RingCT/type: yes/0
Extra: 01b2d8a0a5a3da38c299ebf8bac85610cdae6b9536328addd81ca169ff283d7755021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae56fcaac4ebbd9d053f295969236f079339d6e293a8259e3d9724877f5a3d4b 0.600000000000 1644101 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": 1158482, "vin": [ { "gen": { "height": 1158472 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae56fcaac4ebbd9d053f295969236f079339d6e293a8259e3d9724877f5a3d4b" } } ], "extra": [ 1, 178, 216, 160, 165, 163, 218, 56, 194, 153, 235, 248, 186, 200, 86, 16, 205, 174, 107, 149, 54, 50, 138, 221, 216, 28, 161, 105, 255, 40, 61, 119, 85, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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