Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 826f10b3f29d4f187b4e010d740c022f98da81b26e60b20be0637c576b2ba80a

Tx prefix hash: 1f1ed9f483d1c042dbd3161ee4ad0ec21bc8b886b57be675c95d7463ff561398
Tx public key: cbd237c4d8509f2fb720f723c202eb509b8b154dc11ef02836ab880a824f6c69
Timestamp: 1721937052 Timestamp [UCT]: 2024-07-25 19:50:52 Age [y:d:h:m:s]: 00:256:17:40:13
Block: 1073607 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183399 RingCT/type: yes/0
Extra: 01cbd237c4d8509f2fb720f723c202eb509b8b154dc11ef02836ab880a824f6c69021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f8ee6e1be48e8461f9b248ca39f91ed4f76e7b6503ff90f498c4844c6bcd4d6e 0.600000000000 1546112 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": 1073617, "vin": [ { "gen": { "height": 1073607 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f8ee6e1be48e8461f9b248ca39f91ed4f76e7b6503ff90f498c4844c6bcd4d6e" } } ], "extra": [ 1, 203, 210, 55, 196, 216, 80, 159, 47, 183, 32, 247, 35, 194, 2, 235, 80, 155, 139, 21, 77, 193, 30, 240, 40, 54, 171, 136, 10, 130, 79, 108, 105, 2, 17, 0, 0, 0, 1, 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