Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 949ded9f49d772e314c2a440d53c101ac8ae32e267580bda767a26633319ae58

Tx prefix hash: ef0bc3f7ea7ab364ead7d6f9038b3752d4ccb8d9ec9591c7995c9c6d0aa5b815
Tx public key: e4482b8756dbcfc39c54efedae950bcb58475d4184c1864944b522ee5f45e494
Timestamp: 1734237301 Timestamp [UCT]: 2024-12-15 04:35:01 Age [y:d:h:m:s]: 00:095:02:19:37
Block: 1175496 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67752 RingCT/type: yes/0
Extra: 01e4482b8756dbcfc39c54efedae950bcb58475d4184c1864944b522ee5f45e494021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a6d4289a6f45666a3366d885e25c3c8a05b0304f6c3ec321e43cdfa1a148a9e9 0.600000000000 1661783 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": 1175506, "vin": [ { "gen": { "height": 1175496 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a6d4289a6f45666a3366d885e25c3c8a05b0304f6c3ec321e43cdfa1a148a9e9" } } ], "extra": [ 1, 228, 72, 43, 135, 86, 219, 207, 195, 156, 84, 239, 237, 174, 149, 11, 203, 88, 71, 93, 65, 132, 193, 134, 73, 68, 181, 34, 238, 95, 69, 228, 148, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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