Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3748b55b3c67ac50cc1959148dae6660b98d8cd45b2e0da68df0bd9c17266b5c

Tx prefix hash: 9ff84d20584e88ba9c2ab7ef445b137ad9dc09aafcd56c0355ae31b85b517ae3
Tx public key: f081e0351f9e52a97dff12e0710d1810a6f9eeb7986d1b924520ba4127846df4
Timestamp: 1725476044 Timestamp [UCT]: 2024-09-04 18:54:04 Age [y:d:h:m:s]: 00:224:10:53:57
Block: 1102955 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160271 RingCT/type: yes/0
Extra: 01f081e0351f9e52a97dff12e0710d1810a6f9eeb7986d1b924520ba4127846df4021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e006e2cc1e534c48959fa6371880d818cabec7f5b00a1721ba207f374e43bfec 0.600000000000 1579600 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": 1102965, "vin": [ { "gen": { "height": 1102955 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e006e2cc1e534c48959fa6371880d818cabec7f5b00a1721ba207f374e43bfec" } } ], "extra": [ 1, 240, 129, 224, 53, 31, 158, 82, 169, 125, 255, 18, 224, 113, 13, 24, 16, 166, 249, 238, 183, 152, 109, 27, 146, 69, 32, 186, 65, 39, 132, 109, 244, 2, 17, 0, 0, 0, 1, 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