Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2bfb7a81d9d0d8feca74bf56f54b5fa9c63ce25c0ac744391b270596419cc957

Tx prefix hash: 17ecfc99a73753f1c9a9476745f52816313ae2d56526ca49cb89d571f835af46
Tx public key: c200b7c573868f281deee7d2eb1384a7ba6957158908c696908787fedc9ea767
Timestamp: 1582995158 Timestamp [UCT]: 2020-02-29 16:52:38 Age [y:d:h:m:s]: 04:338:18:47:07
Block: 74259 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1135498 RingCT/type: yes/0
Extra: 01c200b7c573868f281deee7d2eb1384a7ba6957158908c696908787fedc9ea76702110000003e03d36d11000000000000000000

1 output(s) for total of 348.304927325000 dcy

stealth address amount amount idx
00: 572ac9afb82f86ae5547b8e4372e9c94a3b5014a26ea2783be2a1e3a6c4852f6 348.304927325000 137327 of 0

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": 74269, "vin": [ { "gen": { "height": 74259 } } ], "vout": [ { "amount": 348304927325, "target": { "key": "572ac9afb82f86ae5547b8e4372e9c94a3b5014a26ea2783be2a1e3a6c4852f6" } } ], "extra": [ 1, 194, 0, 183, 197, 115, 134, 143, 40, 29, 238, 231, 210, 235, 19, 132, 167, 186, 105, 87, 21, 137, 8, 198, 150, 144, 135, 135, 254, 220, 158, 167, 103, 2, 17, 0, 0, 0, 62, 3, 211, 109, 17, 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