Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a16b42cc077939584df1c380de82bc6828d8dd633379f7b547721c228d8216a2

Tx prefix hash: 47286bce8dc1d2c9cd79dd8cf6f4fa45e864f05d61b78320d934a61a86bfbd75
Tx public key: 77fdc5472ef3c9b9711613975b90cc97935940b0ea870e8d55e93330e4d6e958
Timestamp: 1629078197 Timestamp [UCT]: 2021-08-16 01:43:17 Age [y:d:h:m:s]: 03:104:12:34:25
Block: 314988 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 847902 RingCT/type: yes/0
Extra: 0177fdc5472ef3c9b9711613975b90cc97935940b0ea870e8d55e93330e4d6e95802110000000301f1e57f000000000000000000

1 output(s) for total of 55.502745541000 dcy

stealth address amount amount idx
00: 08e2b511b1dc253cabda5e8df5a763686af7e0d0e963e56e2a9fb5e54b977dc9 55.502745541000 655681 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": 314998, "vin": [ { "gen": { "height": 314988 } } ], "vout": [ { "amount": 55502745541, "target": { "key": "08e2b511b1dc253cabda5e8df5a763686af7e0d0e963e56e2a9fb5e54b977dc9" } } ], "extra": [ 1, 119, 253, 197, 71, 46, 243, 201, 185, 113, 22, 19, 151, 91, 144, 204, 151, 147, 89, 64, 176, 234, 135, 14, 141, 85, 233, 51, 48, 228, 214, 233, 88, 2, 17, 0, 0, 0, 3, 1, 241, 229, 127, 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