Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a427811010a2b62c18d4c9b9e83e10f024718b62a1d5df737b0ec37e7beadab8

Tx prefix hash: 367c4f6b2c4a2a306490a94adb2a2b048c2b3afa2fa746e77eb5182b016669d5
Tx public key: 13c8b025250cee479efeb22472ea58c4468a0fcd8c3a77377dbc9900c3885934
Timestamp: 1727017411 Timestamp [UCT]: 2024-09-22 15:03:31 Age [y:d:h:m:s]: 00:122:14:04:22
Block: 1115737 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 87611 RingCT/type: yes/0
Extra: 0113c8b025250cee479efeb22472ea58c4468a0fcd8c3a77377dbc9900c3885934021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b3a79f9aa4fff2262198ebdd4401c639e7162d50af68552118c62f75507a2990 0.600000000000 1595974 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": 1115747, "vin": [ { "gen": { "height": 1115737 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b3a79f9aa4fff2262198ebdd4401c639e7162d50af68552118c62f75507a2990" } } ], "extra": [ 1, 19, 200, 176, 37, 37, 12, 238, 71, 158, 254, 178, 36, 114, 234, 88, 196, 70, 138, 15, 205, 140, 58, 119, 55, 125, 188, 153, 0, 195, 136, 89, 52, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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