Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 617bfca37f2326d5466b682c68266590db46779823f4de2a6d613653dbe6f82a

Tx prefix hash: 113b5b7234bbc3ef7d79ddd92cc7d7a60d0e06fa0eceff667acbd66d5a9037f0
Tx public key: 4ed4a4133c382743128a1ea18aca14a10cc4b2b6b6e9eff8dc3cae261b37f801
Timestamp: 1602855133 Timestamp [UCT]: 2020-10-16 13:32:13 Age [y:d:h:m:s]: 05:038:15:50:17
Block: 141708 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1276465 RingCT/type: yes/0
Extra: 014ed4a4133c382743128a1ea18aca14a10cc4b2b6b6e9eff8dc3cae261b37f8010211000001f62b5659aa000000000000000000

1 output(s) for total of 208.191633660000 dcy

stealth address amount amount idx
00: 4ee93176775ab8e8f73c36c5d1d031fd9b458d1f27e9f09edf6c6fb98b27ebc1 208.191633660000 235352 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": 141718, "vin": [ { "gen": { "height": 141708 } } ], "vout": [ { "amount": 208191633660, "target": { "key": "4ee93176775ab8e8f73c36c5d1d031fd9b458d1f27e9f09edf6c6fb98b27ebc1" } } ], "extra": [ 1, 78, 212, 164, 19, 60, 56, 39, 67, 18, 138, 30, 161, 138, 202, 20, 161, 12, 196, 178, 182, 182, 233, 239, 248, 220, 60, 174, 38, 27, 55, 248, 1, 2, 17, 0, 0, 1, 246, 43, 86, 89, 170, 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