Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d65f3ec0dbe39b6f6b998e4a8d9600c16003a58abc9abdf66e7d4d5d8deeb6f

Tx prefix hash: cbef1083c37485b547e8b0c9fca04253839cc2c4d6d8aab67550007912928c6c
Tx public key: ab2fe015f4814ba39887e9dd3e176395b45661729e24798077a306d71d2e060d
Timestamp: 1702041282 Timestamp [UCT]: 2023-12-08 13:14:42 Age [y:d:h:m:s]: 01:192:18:45:55
Block: 908661 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 398856 RingCT/type: yes/0
Extra: 01ab2fe015f4814ba39887e9dd3e176395b45661729e24798077a306d71d2e060d021100000003faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bcf04b58fbc8a3f0c9649ca5c81bcc8b6769c66a49fb6352691adde4f4cd9d53 0.600000000000 1365706 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": 908671, "vin": [ { "gen": { "height": 908661 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bcf04b58fbc8a3f0c9649ca5c81bcc8b6769c66a49fb6352691adde4f4cd9d53" } } ], "extra": [ 1, 171, 47, 224, 21, 244, 129, 75, 163, 152, 135, 233, 221, 62, 23, 99, 149, 180, 86, 97, 114, 158, 36, 121, 128, 119, 163, 6, 215, 29, 46, 6, 13, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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