Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3856232dac25e3fc2b3f1fee59dfa60062ac4986e9d143e002c090ba42a63d6a

Tx prefix hash: 744637208d1851909bcef5aa0d775287e8fb9def1c3f8250d24172315259b8b5
Tx public key: 403c3239ac7ed48db72891a94da48766c1d875c1a82864aec4db72f57cdb89af
Timestamp: 1578159423 Timestamp [UCT]: 2020-01-04 17:37:03 Age [y:d:h:m:s]: 04:306:18:59:38
Block: 38691 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1108390 RingCT/type: yes/0
Extra: 01403c3239ac7ed48db72891a94da48766c1d875c1a82864aec4db72f57cdb89af0211000000552264afe6000000000000000000

1 output(s) for total of 456.879324610000 dcy

stealth address amount amount idx
00: c41efaca68b387d46a0275a56d4f9e7ded9b4e8fbec2a4db0ddc26eb6b524a19 456.879324610000 66143 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": 38701, "vin": [ { "gen": { "height": 38691 } } ], "vout": [ { "amount": 456879324610, "target": { "key": "c41efaca68b387d46a0275a56d4f9e7ded9b4e8fbec2a4db0ddc26eb6b524a19" } } ], "extra": [ 1, 64, 60, 50, 57, 172, 126, 212, 141, 183, 40, 145, 169, 77, 164, 135, 102, 193, 216, 117, 193, 168, 40, 100, 174, 196, 219, 114, 245, 124, 219, 137, 175, 2, 17, 0, 0, 0, 85, 34, 100, 175, 230, 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