Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aea1274a959ffb8e9e7cc28991f5a28813e5f180d12b03d20f472166876d5c8f

Tx prefix hash: 5fece0687610eafa610faafa7cd2c4007424a45d46b17fa330c87431e5f28a07
Tx public key: 54ec6d0c54fed9ea76880500a426c0e25eaebfaf443b35b4c42ecf29c7e20876
Timestamp: 1578241912 Timestamp [UCT]: 2020-01-05 16:31:52 Age [y:d:h:m:s]: 05:035:08:02:57
Block: 39318 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1175119 RingCT/type: yes/0
Extra: 0154ec6d0c54fed9ea76880500a426c0e25eaebfaf443b35b4c42ecf29c7e208760211000000034ac5aa02000000000000000000

1 output(s) for total of 454.706833586000 dcy

stealth address amount amount idx
00: 20dd8fa2114eb1e5462ab5ea767a5f1bfadfb16cd59c35efb1bb1261757230e6 454.706833586000 67709 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": 39328, "vin": [ { "gen": { "height": 39318 } } ], "vout": [ { "amount": 454706833586, "target": { "key": "20dd8fa2114eb1e5462ab5ea767a5f1bfadfb16cd59c35efb1bb1261757230e6" } } ], "extra": [ 1, 84, 236, 109, 12, 84, 254, 217, 234, 118, 136, 5, 0, 164, 38, 192, 226, 94, 174, 191, 175, 68, 59, 53, 180, 196, 46, 207, 41, 199, 226, 8, 118, 2, 17, 0, 0, 0, 3, 74, 197, 170, 2, 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