Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14dfc16630a642737c64858b3d2a5619d7f47ab1af69aad1487679800d7b6b6f

Tx prefix hash: 8a0ab172e46dcdce2e7febe546a3bc798bb65be4f146e1442f33a48a652708fc
Tx public key: ae1c94d80ec2f95dcf850e3f3018ff7ccf1c1634ea891195ccb153e292f2e913
Timestamp: 1746153582 Timestamp [UCT]: 2025-05-02 02:39:42 Age [y:d:h:m:s]: 00:203:06:07:45
Block: 1273853 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142975 RingCT/type: yes/0
Extra: 01ae1c94d80ec2f95dcf850e3f3018ff7ccf1c1634ea891195ccb153e292f2e9130211000000029f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 08b77789c8aa4f26fdb62624be8292ada7d07ad4a71a7a4fbc10bc1a13fa3c2f 0.600000000000 1761140 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": 1273863, "vin": [ { "gen": { "height": 1273853 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08b77789c8aa4f26fdb62624be8292ada7d07ad4a71a7a4fbc10bc1a13fa3c2f" } } ], "extra": [ 1, 174, 28, 148, 216, 14, 194, 249, 93, 207, 133, 14, 63, 48, 24, 255, 124, 207, 28, 22, 52, 234, 137, 17, 149, 204, 177, 83, 226, 146, 242, 233, 19, 2, 17, 0, 0, 0, 2, 159, 159, 230, 140, 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