Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d28b68cb180655162048fc8da8223532fea849cb29fca1790253b32019d14e9

Tx prefix hash: 78f9822d7b6af4e7fed594869463c008524be2d5adbf906c6d220b9983795e2c
Tx public key: d302952c095d0eb6aa72d52ea2208ca061f6ca7d2e24fcf346f2ecda1099b9d0
Timestamp: 1723733360 Timestamp [UCT]: 2024-08-15 14:49:20 Age [y:d:h:m:s]: 00:260:03:42:57
Block: 1088511 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185822 RingCT/type: yes/0
Extra: 01d302952c095d0eb6aa72d52ea2208ca061f6ca7d2e24fcf346f2ecda1099b9d0021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6bff267a78ebca10831455d40666c07d4311a45ea9c4489280963b3e2deb6ce6 0.600000000000 1563128 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": 1088521, "vin": [ { "gen": { "height": 1088511 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6bff267a78ebca10831455d40666c07d4311a45ea9c4489280963b3e2deb6ce6" } } ], "extra": [ 1, 211, 2, 149, 44, 9, 93, 14, 182, 170, 114, 213, 46, 162, 32, 140, 160, 97, 246, 202, 125, 46, 36, 252, 243, 70, 242, 236, 218, 16, 153, 185, 208, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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