Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2f1438aeb045a1434d81c421ed08db2afc768e227991b6f4a24f5b55a6df838

Tx prefix hash: c8dd3ccc96321375e89f402c20ce17741dfa7d85851b42ec790297cf84d19b5f
Tx public key: ac599029c5c73cf0f7b6c648c852eb7ae7c603af803a388d7e671b117261d273
Timestamp: 1728875494 Timestamp [UCT]: 2024-10-14 03:11:34 Age [y:d:h:m:s]: 00:041:02:52:13
Block: 1131138 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 29353 RingCT/type: yes/0
Extra: 01ac599029c5c73cf0f7b6c648c852eb7ae7c603af803a388d7e671b117261d27302110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 45ca8790579f7e445c456cdd40742dd4b7559ba069b5eb57b23999f744b5011e 0.600000000000 1614019 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": 1131148, "vin": [ { "gen": { "height": 1131138 } } ], "vout": [ { "amount": 600000000, "target": { "key": "45ca8790579f7e445c456cdd40742dd4b7559ba069b5eb57b23999f744b5011e" } } ], "extra": [ 1, 172, 89, 144, 41, 197, 199, 60, 240, 247, 182, 198, 72, 200, 82, 235, 122, 231, 198, 3, 175, 128, 58, 56, 141, 126, 103, 27, 17, 114, 97, 210, 115, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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