Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a01b34d9bba0f5e32b2ef69402c34ca0a5625450fdc226aec0bef7fa9420ac8c

Tx prefix hash: 4a0271d8546f2f2bbb36d611f72bf55c312db50d782dab7b688368fe2409841d
Tx public key: 00998a2e969e4c13b14b6dd57d64515e954006ae8d2bbabcca34f56338ca4eda
Timestamp: 1672472963 Timestamp [UCT]: 2022-12-31 07:49:23 Age [y:d:h:m:s]: 02:016:08:31:47
Block: 664389 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 533601 RingCT/type: yes/0
Extra: 0100998a2e969e4c13b14b6dd57d64515e954006ae8d2bbabcca34f56338ca4eda021100000002e7ace25d000000000000000000

1 output(s) for total of 3.860143124000 dcy

stealth address amount amount idx
00: 060f609fc7b5f5cec88a5a7c4e1ceaa1535b43583cc9a7a165c90c99c89cab41 3.860143124000 1105364 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": 664399, "vin": [ { "gen": { "height": 664389 } } ], "vout": [ { "amount": 3860143124, "target": { "key": "060f609fc7b5f5cec88a5a7c4e1ceaa1535b43583cc9a7a165c90c99c89cab41" } } ], "extra": [ 1, 0, 153, 138, 46, 150, 158, 76, 19, 177, 75, 109, 213, 125, 100, 81, 94, 149, 64, 6, 174, 141, 43, 186, 188, 202, 52, 245, 99, 56, 202, 78, 218, 2, 17, 0, 0, 0, 2, 231, 172, 226, 93, 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