Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 075f1b1950f39d8cec4687791279e6200dd722f6d95700995220f33e1074f089

Tx prefix hash: 08d765df9386a998a9a10cf4e1856efb01e8d678fb96d4d9edb2abd21f28435f
Tx public key: 8149ddeaa713b92afb1c19249e857b21129092be8cd5aec3423e9d723d55f2d9
Timestamp: 1730272497 Timestamp [UCT]: 2024-10-30 07:14:57 Age [y:d:h:m:s]: 00:025:11:09:34
Block: 1142648 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 18212 RingCT/type: yes/0
Extra: 018149ddeaa713b92afb1c19249e857b21129092be8cd5aec3423e9d723d55f2d9021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fb453ee4ae4410dd33db814d11677e59c34f0a7502f333f06f137f939cd7e9da 0.600000000000 1626503 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": 1142658, "vin": [ { "gen": { "height": 1142648 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fb453ee4ae4410dd33db814d11677e59c34f0a7502f333f06f137f939cd7e9da" } } ], "extra": [ 1, 129, 73, 221, 234, 167, 19, 185, 42, 251, 28, 25, 36, 158, 133, 123, 33, 18, 144, 146, 190, 140, 213, 174, 195, 66, 62, 157, 114, 61, 85, 242, 217, 2, 17, 0, 0, 0, 3, 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