Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 503f00550c5692fc6c8660d0d4eb0159e6d615f3d7e8b9fb06f000a840fcf309

Tx prefix hash: bc3f1fdded298056ab46b042eb398c114eb40e6b53be3bad7e5bdfdca00b878f
Tx public key: 774e8df8c80e5f30b0ef89e4f07023fddbd80cd917594cb353a61ea3ae9ffd42
Timestamp: 1630608705 Timestamp [UCT]: 2021-09-02 18:51:45 Age [y:d:h:m:s]: 03:086:20:57:25
Block: 326111 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 836821 RingCT/type: yes/0
Extra: 01774e8df8c80e5f30b0ef89e4f07023fddbd80cd917594cb353a61ea3ae9ffd420211000001577062e8e6000000000000000000

1 output(s) for total of 50.986985284000 dcy

stealth address amount amount idx
00: b9d45a44275fce122f2d1b0df933a82a67ba1c35068f784b42048958e3ca7bf4 50.986985284000 675762 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": 326121, "vin": [ { "gen": { "height": 326111 } } ], "vout": [ { "amount": 50986985284, "target": { "key": "b9d45a44275fce122f2d1b0df933a82a67ba1c35068f784b42048958e3ca7bf4" } } ], "extra": [ 1, 119, 78, 141, 248, 200, 14, 95, 48, 176, 239, 137, 228, 240, 112, 35, 253, 219, 216, 12, 217, 23, 89, 76, 179, 83, 166, 30, 163, 174, 159, 253, 66, 2, 17, 0, 0, 1, 87, 112, 98, 232, 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