Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4f89f938efc892d8d1441d4ee6e73e03ecadfbbe7cb796f22e81ac320bc91f6

Tx prefix hash: 9f03cc39f04cdc40c2321e9f1ab57f213a8639c0ad8ddaac7b9c9ab711ae2961
Tx public key: 7313feb78ce9a9d0b919ddce13b4afaf9230a39361baa75d7caef79e44a9e8bf
Timestamp: 1735050939 Timestamp [UCT]: 2024-12-24 14:35:39 Age [y:d:h:m:s]: 00:091:06:29:44
Block: 1182226 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 65002 RingCT/type: yes/0
Extra: 017313feb78ce9a9d0b919ddce13b4afaf9230a39361baa75d7caef79e44a9e8bf021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 75a8f5b95a2f473d7bc9ca1b8c313c802bcd96707b6ca4fb96f817be1d2e0d69 0.600000000000 1668659 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": 1182236, "vin": [ { "gen": { "height": 1182226 } } ], "vout": [ { "amount": 600000000, "target": { "key": "75a8f5b95a2f473d7bc9ca1b8c313c802bcd96707b6ca4fb96f817be1d2e0d69" } } ], "extra": [ 1, 115, 19, 254, 183, 140, 233, 169, 208, 185, 25, 221, 206, 19, 180, 175, 175, 146, 48, 163, 147, 97, 186, 167, 93, 124, 174, 247, 158, 68, 169, 232, 191, 2, 17, 0, 0, 0, 5, 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