Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 12495da5e618333cc1f5082247a93b6e1c39e082327207e45d8ec922cde7def1

Tx prefix hash: 86a08dc9af5dc4ab452e61352bd801026a79b2fab0846433cba6e560ec8fc0fe
Tx public key: 6a323345a55c2e11467e675ce0f327ba42108f5d9bd9f28b6cb4a262ec3ed0d5
Timestamp: 1634653627 Timestamp [UCT]: 2021-10-19 14:27:07 Age [y:d:h:m:s]: 04:013:02:01:28
Block: 356222 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1045825 RingCT/type: yes/0
Extra: 016a323345a55c2e11467e675ce0f327ba42108f5d9bd9f28b6cb4a262ec3ed0d5021100000032f29d7abf000000000000000000

1 output(s) for total of 40.522530322000 dcy

stealth address amount amount idx
00: c1df9d4829e9d5bb5d2385181e2a1c2c2324255b98c841ee0a9835e7cd5d4c42 40.522530322000 726902 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": 356232, "vin": [ { "gen": { "height": 356222 } } ], "vout": [ { "amount": 40522530322, "target": { "key": "c1df9d4829e9d5bb5d2385181e2a1c2c2324255b98c841ee0a9835e7cd5d4c42" } } ], "extra": [ 1, 106, 50, 51, 69, 165, 92, 46, 17, 70, 126, 103, 92, 224, 243, 39, 186, 66, 16, 143, 93, 155, 217, 242, 139, 108, 180, 162, 98, 236, 62, 208, 213, 2, 17, 0, 0, 0, 50, 242, 157, 122, 191, 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