Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a835c6e42d496e24d780efb8763ed33f0a9f8b5290d5820c20409af37a0e438

Tx prefix hash: 35fd5ad0fbe37876da54f43469c7ab7f61cc98249a68e6f4fa3f38e5007257ff
Tx public key: 27358ab4b3363d49aa5877889bd80cd56745b9331e1c2cf5f42351c53f7b6fb3
Timestamp: 1736328740 Timestamp [UCT]: 2025-01-08 09:32:20 Age [y:d:h:m:s]: 00:162:12:47:42
Block: 1192791 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115846 RingCT/type: yes/0
Extra: 0127358ab4b3363d49aa5877889bd80cd56745b9331e1c2cf5f42351c53f7b6fb30211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9fdae38d39d4ed377b9bbdefb3c414ab544f68a664d77d00d1b66a7c49775e6 0.600000000000 1679348 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": 1192801, "vin": [ { "gen": { "height": 1192791 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9fdae38d39d4ed377b9bbdefb3c414ab544f68a664d77d00d1b66a7c49775e6" } } ], "extra": [ 1, 39, 53, 138, 180, 179, 54, 61, 73, 170, 88, 119, 136, 155, 216, 12, 213, 103, 69, 185, 51, 30, 28, 44, 245, 244, 35, 81, 197, 63, 123, 111, 179, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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