Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0b948f658fb72cf8fca777942f36ed5d555d834aa5c5331061e33ebab511a83

Tx prefix hash: 98c20d6a6a0835356bf871253487164439961853cbb59b6c912880b2bdf2f729
Tx public key: b1c0e8eff0bb133d77ae22b6cbd42b861547fa07ca335ff1d84192f244e58964
Timestamp: 1726751794 Timestamp [UCT]: 2024-09-19 13:16:34 Age [y:d:h:m:s]: 01:061:15:30:56
Block: 1113530 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 302481 RingCT/type: yes/0
Extra: 01b1c0e8eff0bb133d77ae22b6cbd42b861547fa07ca335ff1d84192f244e58964021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 06c068d0991cb057d0f7897e36a119b51b3ea0059b51564f4f0492f73e4cc4fb 0.600000000000 1593233 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": 1113540, "vin": [ { "gen": { "height": 1113530 } } ], "vout": [ { "amount": 600000000, "target": { "key": "06c068d0991cb057d0f7897e36a119b51b3ea0059b51564f4f0492f73e4cc4fb" } } ], "extra": [ 1, 177, 192, 232, 239, 240, 187, 19, 61, 119, 174, 34, 182, 203, 212, 43, 134, 21, 71, 250, 7, 202, 51, 95, 241, 216, 65, 146, 242, 68, 229, 137, 100, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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