Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dcd3a8aaef4831b5b7bac44bb1555bcbcc09f94249961dc0e0d4cdca2316f206

Tx prefix hash: 32ab969e693c11e9c2882e00b475d61035d1eb7002d10aa0e70950b3490271d6
Tx public key: f7b2eaf0e7a69dd461771e48340afc3da739def8558e9d8d58b44f37d722fde4
Timestamp: 1735218193 Timestamp [UCT]: 2024-12-26 13:03:13 Age [y:d:h:m:s]: 00:108:13:07:12
Block: 1183633 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77355 RingCT/type: yes/0
Extra: 01f7b2eaf0e7a69dd461771e48340afc3da739def8558e9d8d58b44f37d722fde4021100000018007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 138f2864d4acace6e2b5adf029edc0c33914d794201c77e6939de28bb5e93ef2 0.600000000000 1670080 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": 1183643, "vin": [ { "gen": { "height": 1183633 } } ], "vout": [ { "amount": 600000000, "target": { "key": "138f2864d4acace6e2b5adf029edc0c33914d794201c77e6939de28bb5e93ef2" } } ], "extra": [ 1, 247, 178, 234, 240, 231, 166, 157, 212, 97, 119, 30, 72, 52, 10, 252, 61, 167, 57, 222, 248, 85, 142, 157, 141, 88, 180, 79, 55, 215, 34, 253, 228, 2, 17, 0, 0, 0, 24, 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