Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 13825ef70348aafbae33695220d37f91ce78e1dc968cc534338101ec2c73a30e

Tx prefix hash: cacd1d1396da9f196e3b2568f7256f6fde7f46ef18d889fe83b2622b9dc726d9
Tx public key: cd8427d4bda94fa798312e8f8e120c8452be0e1f1f68882aa5d2bfc3076d8b4f
Timestamp: 1731189118 Timestamp [UCT]: 2024-11-09 21:51:58 Age [y:d:h:m:s]: 00:130:21:27:01
Block: 1150237 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93381 RingCT/type: yes/0
Extra: 01cd8427d4bda94fa798312e8f8e120c8452be0e1f1f68882aa5d2bfc3076d8b4f021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e38015bb1302ec57aace39c2e4e4471e9d0e21404e1aacc4bbac356547e06776 0.600000000000 1635490 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": 1150247, "vin": [ { "gen": { "height": 1150237 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e38015bb1302ec57aace39c2e4e4471e9d0e21404e1aacc4bbac356547e06776" } } ], "extra": [ 1, 205, 132, 39, 212, 189, 169, 79, 167, 152, 49, 46, 143, 142, 18, 12, 132, 82, 190, 14, 31, 31, 104, 136, 42, 165, 210, 191, 195, 7, 109, 139, 79, 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