Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a1f846a1dda6d41aa32fe61d6d9b7a6a25ceb3557f6553ff3dd994c7e37693d

Tx prefix hash: 5a79674d78fb3fd02282d328eed04d5ebde696be8ffd17ac49abe735a267555f
Tx public key: 0d3226cbe905e49a48236e8da70ecacd4994a5ae84019a33f03abc215318168f
Timestamp: 1736623914 Timestamp [UCT]: 2025-01-11 19:31:54 Age [y:d:h:m:s]: 00:339:19:04:58
Block: 1195226 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 240406 RingCT/type: yes/0
Extra: 010d3226cbe905e49a48236e8da70ecacd4994a5ae84019a33f03abc215318168f02110000000b1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ca3eb55a3144215dd9f127c0ef4040a1865dc2861eb2f3b06957cd57629229ef 0.600000000000 1681815 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": 1195236, "vin": [ { "gen": { "height": 1195226 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ca3eb55a3144215dd9f127c0ef4040a1865dc2861eb2f3b06957cd57629229ef" } } ], "extra": [ 1, 13, 50, 38, 203, 233, 5, 228, 154, 72, 35, 110, 141, 167, 14, 202, 205, 73, 148, 165, 174, 132, 1, 154, 51, 240, 58, 188, 33, 83, 24, 22, 143, 2, 17, 0, 0, 0, 11, 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