Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c9ac5b5db3640ff89d53266cb127243fe90d643c2d9c6632760dae03970d8e3

Tx prefix hash: 08100159d03e8aed58a9e72e5b6014c5990f4d189362138e2ebc1e9ecec35e01
Tx public key: 8722c2c4cdef4eb44ad4c9872c6e2202b862318897fec30920690aa433e555da
Timestamp: 1577838997 Timestamp [UCT]: 2020-01-01 00:36:37 Age [y:d:h:m:s]: 05:002:13:26:27
Block: 36065 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1151859 RingCT/type: yes/0
Extra: 018722c2c4cdef4eb44ad4c9872c6e2202b862318897fec30920690aa433e555da02110000001a8a2ee0d9000000000000000000

1 output(s) for total of 466.133201051000 dcy

stealth address amount amount idx
00: cf259218da0a96f77aa12a59206f571f18c3afcc96734d5c1d8e79e48d81bdf3 466.133201051000 60961 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": 36075, "vin": [ { "gen": { "height": 36065 } } ], "vout": [ { "amount": 466133201051, "target": { "key": "cf259218da0a96f77aa12a59206f571f18c3afcc96734d5c1d8e79e48d81bdf3" } } ], "extra": [ 1, 135, 34, 194, 196, 205, 239, 78, 180, 74, 212, 201, 135, 44, 110, 34, 2, 184, 98, 49, 136, 151, 254, 195, 9, 32, 105, 10, 164, 51, 229, 85, 218, 2, 17, 0, 0, 0, 26, 138, 46, 224, 217, 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