Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7bc3ed1b8a28c91448734928ac50fd05c0216b80e49b3112abfcb61bfedb4e2e

Tx prefix hash: 3ac576608a65c81a66b2caa53c2d423d8939eea5e436a59f5bf1f5cdffdc1320
Tx public key: 2cd81d068732abdbbc7e9fc65b6729c71d46b7a3cadd41b66c255029a3ec86fd
Timestamp: 1755049856 Timestamp [UCT]: 2025-08-13 01:50:56 Age [y:d:h:m:s]: 00:045:17:17:59
Block: 1345765 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 31999 RingCT/type: yes/0
Extra: 012cd81d068732abdbbc7e9fc65b6729c71d46b7a3cadd41b66c255029a3ec86fd0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1aaf9ef65651fe43eff8d4fa27e88310d36bd98daea24462d3bc4ea590d9c2bd 0.600000000000 1833660 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": 1345775, "vin": [ { "gen": { "height": 1345765 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1aaf9ef65651fe43eff8d4fa27e88310d36bd98daea24462d3bc4ea590d9c2bd" } } ], "extra": [ 1, 44, 216, 29, 6, 135, 50, 171, 219, 188, 126, 159, 198, 91, 103, 41, 199, 29, 70, 183, 163, 202, 221, 65, 182, 108, 37, 80, 41, 163, 236, 134, 253, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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