Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9226fc4898ee385114adc9c2f4b0c04ead85e8080e95dbd3417e7417396a977

Tx prefix hash: 36316105f1b10a7fac0e3cb6fda2ccc0b9d870dddd9db77387e9e8ab895ee72c
Tx public key: e91a9712b3eefb58f83cf3aa1a8f1533beef3dce1a9a5a1143177e1f0f6d109d
Timestamp: 1719543861 Timestamp [UCT]: 2024-06-28 03:04:21 Age [y:d:h:m:s]: 01:136:06:37:16
Block: 1053769 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 355943 RingCT/type: yes/0
Extra: 01e91a9712b3eefb58f83cf3aa1a8f1533beef3dce1a9a5a1143177e1f0f6d109d02110000000a7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 84f23bab67786e7e1df2c0ee965ff6a3cce6995bb848be6c0e270fd935bf4bff 0.600000000000 1524120 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": 1053779, "vin": [ { "gen": { "height": 1053769 } } ], "vout": [ { "amount": 600000000, "target": { "key": "84f23bab67786e7e1df2c0ee965ff6a3cce6995bb848be6c0e270fd935bf4bff" } } ], "extra": [ 1, 233, 26, 151, 18, 179, 238, 251, 88, 248, 60, 243, 170, 26, 143, 21, 51, 190, 239, 61, 206, 26, 154, 90, 17, 67, 23, 126, 31, 15, 109, 16, 157, 2, 17, 0, 0, 0, 10, 122, 156, 244, 199, 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