Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8722be7c0498c3a322158596e7bcbfe7370f0458fb9f395bfbf81b81356eacf

Tx prefix hash: 2688ff79ac9b12e50feb19cb2fe2db7c6afb5a0b76fd18d0165ee40be8d4b4b1
Tx public key: abe1db6504bedb40a2bf719440c93313cd17a94866f8ee1c91c72bb1a1babb09
Timestamp: 1706900843 Timestamp [UCT]: 2024-02-02 19:07:23 Age [y:d:h:m:s]: 01:134:11:02:01
Block: 948940 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 357113 RingCT/type: yes/0
Extra: 01abe1db6504bedb40a2bf719440c93313cd17a94866f8ee1c91c72bb1a1babb090211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5a31d07b685f51dbf3d811b076cf8531a234b6fd9247b7ee67e03d994c476a75 0.600000000000 1407456 of 15

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": 948950, "vin": [ { "gen": { "height": 948940 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5a31d07b685f51dbf3d811b076cf8531a234b6fd9247b7ee67e03d994c476a75" } } ], "extra": [ 1, 171, 225, 219, 101, 4, 190, 219, 64, 162, 191, 113, 148, 64, 201, 51, 19, 205, 23, 169, 72, 102, 248, 238, 28, 145, 199, 43, 177, 161, 186, 187, 9, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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