Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a223c4115734acfb5cd4db697d2c1fb63718d18cb19c27241e91cb29766c7831

Tx prefix hash: c3e38e8b2bc2c18f1fb97901f43972fe200d5f4a5f5a1b8961a2c6e6466dd78e
Tx public key: f9478eb669cd8c362c71c8d72d202d5d82010b1263d1183fe0ff3dd56450f8b8
Timestamp: 1709425812 Timestamp [UCT]: 2024-03-03 00:30:12 Age [y:d:h:m:s]: 00:270:19:02:25
Block: 969894 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193868 RingCT/type: yes/0
Extra: 01f9478eb669cd8c362c71c8d72d202d5d82010b1263d1183fe0ff3dd56450f8b80211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5937f5f56dd70507ebc0fb369302af5708e702f80ec8fe39c5a8b30684399106 0.600000000000 1429743 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": 969904, "vin": [ { "gen": { "height": 969894 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5937f5f56dd70507ebc0fb369302af5708e702f80ec8fe39c5a8b30684399106" } } ], "extra": [ 1, 249, 71, 142, 182, 105, 205, 140, 54, 44, 113, 200, 215, 45, 32, 45, 93, 130, 1, 11, 18, 99, 209, 24, 63, 224, 255, 61, 213, 100, 80, 248, 184, 2, 17, 0, 0, 0, 3, 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