Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3bf3df37057a53646f132e65649dbb28313e6c068337d7387f565c6907b3b4df

Tx prefix hash: 47fb29f82536ce18696731df1072162762506e314eb0c24f701e7b3cc952c2dd
Tx public key: 706be7f80814f8d007d3a7920eb00d4f0345abc5211a83810338c0ff1add3b5c
Timestamp: 1717465625 Timestamp [UCT]: 2024-06-04 01:47:05 Age [y:d:h:m:s]: 00:287:03:38:16
Block: 1036546 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205219 RingCT/type: yes/0
Extra: 01706be7f80814f8d007d3a7920eb00d4f0345abc5211a83810338c0ff1add3b5c02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e4cfeb7ef8aa3b11c5df6f8bd81a6b5529413641c8649257731c0076823b7ab 0.600000000000 1505073 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": 1036556, "vin": [ { "gen": { "height": 1036546 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e4cfeb7ef8aa3b11c5df6f8bd81a6b5529413641c8649257731c0076823b7ab" } } ], "extra": [ 1, 112, 107, 231, 248, 8, 20, 248, 208, 7, 211, 167, 146, 14, 176, 13, 79, 3, 69, 171, 197, 33, 26, 131, 129, 3, 56, 192, 255, 26, 221, 59, 92, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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