Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 638f1777f816c62348fa662bc767265be6d3f59c7b770af9ccd7e18f06bdcc27

Tx prefix hash: b72727187a69124161dc1a8ce27c12848cf59a8e959e44ab8a031b803c2c91a3
Tx public key: 13a0335c3070fdac80683dbcf82f9b0ed1e7b543da66f808b0e973f74423bc71
Timestamp: 1700858994 Timestamp [UCT]: 2023-11-24 20:49:54 Age [y:d:h:m:s]: 01:201:14:38:38
Block: 898869 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 405243 RingCT/type: yes/0
Extra: 0113a0335c3070fdac80683dbcf82f9b0ed1e7b543da66f808b0e973f74423bc71021100000003faf35c9c000000000000000000

1 output(s) for total of 0.645169532000 dcy

stealth address amount amount idx
00: 1efc2e6441efb995d43f80ada6afa59b92edd8eae2a5a9f20b1ca0fc0c662932 0.645169532000 1355306 of 0

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": 898879, "vin": [ { "gen": { "height": 898869 } } ], "vout": [ { "amount": 645169532, "target": { "key": "1efc2e6441efb995d43f80ada6afa59b92edd8eae2a5a9f20b1ca0fc0c662932" } } ], "extra": [ 1, 19, 160, 51, 92, 48, 112, 253, 172, 128, 104, 61, 188, 248, 47, 155, 14, 209, 231, 181, 67, 218, 102, 248, 8, 176, 233, 115, 247, 68, 35, 188, 113, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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