Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 115f37305bdf56b6e24e5fa533e23838f4771fc956a3f735aa3fda1bad9aaf76

Tx prefix hash: 0047e217f42015184db001721d95c90df0308edc53f0286ad45965c38c60f1bb
Tx public key: 0f0e1c275d88198d7ac9fcada63f1c8bc8b4db6613b70c19d0ff42e137911db3
Timestamp: 1612790551 Timestamp [UCT]: 2021-02-08 13:22:31 Age [y:d:h:m:s]: 03:285:12:04:20
Block: 194562 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 962937 RingCT/type: yes/0
Extra: 010f0e1c275d88198d7ac9fcada63f1c8bc8b4db6613b70c19d0ff42e137911db3021100000213c6b81c9d000000000000000000

1 output(s) for total of 139.107647651000 dcy

stealth address amount amount idx
00: c8d1eaf0f7b0ac4528737e4eebe591c04aa54cb7f2052734e376bf2a1c79ca37 139.107647651000 395136 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": 194572, "vin": [ { "gen": { "height": 194562 } } ], "vout": [ { "amount": 139107647651, "target": { "key": "c8d1eaf0f7b0ac4528737e4eebe591c04aa54cb7f2052734e376bf2a1c79ca37" } } ], "extra": [ 1, 15, 14, 28, 39, 93, 136, 25, 141, 122, 201, 252, 173, 166, 63, 28, 139, 200, 180, 219, 102, 19, 183, 12, 25, 208, 255, 66, 225, 55, 145, 29, 179, 2, 17, 0, 0, 2, 19, 198, 184, 28, 157, 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