Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f75085851d8caedea88315a960a0fe77bbd8ecacce16186cabf3a2bcea96002

Tx prefix hash: 9e1e09f9e1b75ee5777f71a6acf09f4468d52aab773c4223579acd66b7f063ce
Tx public key: 7e5ca2c7628a216639911aabce9efaed79719d779fcc62458c01c9451a3a432b
Timestamp: 1712527495 Timestamp [UCT]: 2024-04-07 22:04:55 Age [y:d:h:m:s]: 01:068:23:34:04
Block: 995574 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 310230 RingCT/type: yes/0
Extra: 017e5ca2c7628a216639911aabce9efaed79719d779fcc62458c01c9451a3a432b02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 37d952a4751bfb9aa5b4dca8a1b9bb6201f71c50d80e8e80a01ad7bdc4e18565 0.600000000000 1455984 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": 995584, "vin": [ { "gen": { "height": 995574 } } ], "vout": [ { "amount": 600000000, "target": { "key": "37d952a4751bfb9aa5b4dca8a1b9bb6201f71c50d80e8e80a01ad7bdc4e18565" } } ], "extra": [ 1, 126, 92, 162, 199, 98, 138, 33, 102, 57, 145, 26, 171, 206, 158, 250, 237, 121, 113, 157, 119, 159, 204, 98, 69, 140, 1, 201, 69, 26, 58, 67, 43, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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