Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aff0cb52e5372a11009d04f044fe282dba1a402e439ea81d20ec70da6a66ba90

Tx prefix hash: e346e692ab58f08e19b6ed6a74d63a00b948ebc40339e7565551e3618baa2d4e
Tx public key: 2192e9f550eb1f01e914caa7e9885a7dc17ae6e76203571969dd9e1b5548d9a6
Timestamp: 1729411521 Timestamp [UCT]: 2024-10-20 08:05:21 Age [y:d:h:m:s]: 00:155:03:48:54
Block: 1135574 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110664 RingCT/type: yes/0
Extra: 012192e9f550eb1f01e914caa7e9885a7dc17ae6e76203571969dd9e1b5548d9a6021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3a382516c6edbb83243d792d84efecff32f41be0b418d97b68bcd365536f352e 0.600000000000 1618913 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": 1135584, "vin": [ { "gen": { "height": 1135574 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a382516c6edbb83243d792d84efecff32f41be0b418d97b68bcd365536f352e" } } ], "extra": [ 1, 33, 146, 233, 245, 80, 235, 31, 1, 233, 20, 202, 167, 233, 136, 90, 125, 193, 122, 230, 231, 98, 3, 87, 25, 105, 221, 158, 27, 85, 72, 217, 166, 2, 17, 0, 0, 0, 5, 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