Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa92a37d82c53e1081bb6ef77d7800475242b0dfa093bcc0833d209756624645

Tx prefix hash: 415753640c1c53cefb7ffc06b2815e55539919017624278e6c8edef96d423704
Tx public key: ee34b7f57e1ddb067162c19bf2c951e7d54d652a1355e2b49606239c81f689b4
Timestamp: 1747195482 Timestamp [UCT]: 2025-05-14 04:04:42 Age [y:d:h:m:s]: 00:223:18:44:50
Block: 1282487 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157677 RingCT/type: yes/0
Extra: 01ee34b7f57e1ddb067162c19bf2c951e7d54d652a1355e2b49606239c81f689b40211000000079f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bfafc7c8bede215f6a073a8ffe9ae8f30d96a275373f4ea1c1d524cf93b5bf82 0.600000000000 1769894 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": 1282497, "vin": [ { "gen": { "height": 1282487 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bfafc7c8bede215f6a073a8ffe9ae8f30d96a275373f4ea1c1d524cf93b5bf82" } } ], "extra": [ 1, 238, 52, 183, 245, 126, 29, 219, 6, 113, 98, 193, 155, 242, 201, 81, 231, 213, 77, 101, 42, 19, 85, 226, 180, 150, 6, 35, 156, 129, 246, 137, 180, 2, 17, 0, 0, 0, 7, 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