Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b14216a5c2e80e1267a63e3be629aa1134c7403a0b6acdb9ca58905b444789e0

Tx prefix hash: 034d9039a079917b5d527db134882a3c38effaca4b171caa6310bf697f59715c
Tx public key: e5297887714ff549757ba6c22cc269d7b7fd206d9d1e8a292f452ba227d8552d
Timestamp: 1617078320 Timestamp [UCT]: 2021-03-30 04:25:20 Age [y:d:h:m:s]: 03:348:08:45:11
Block: 229456 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1008252 RingCT/type: yes/0
Extra: 01e5297887714ff549757ba6c22cc269d7b7fd206d9d1e8a292f452ba227d8552d0211000000a24405d762000000000000000000

1 output(s) for total of 106.592129909000 dcy

stealth address amount amount idx
00: a31f2b49f107c40e8d344ad65bea54c1e93e667b8462d67d42d162a7abec8771 106.592129909000 476090 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": 229466, "vin": [ { "gen": { "height": 229456 } } ], "vout": [ { "amount": 106592129909, "target": { "key": "a31f2b49f107c40e8d344ad65bea54c1e93e667b8462d67d42d162a7abec8771" } } ], "extra": [ 1, 229, 41, 120, 135, 113, 79, 245, 73, 117, 123, 166, 194, 44, 194, 105, 215, 183, 253, 32, 109, 157, 30, 138, 41, 47, 69, 43, 162, 39, 216, 85, 45, 2, 17, 0, 0, 0, 162, 68, 5, 215, 98, 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