Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25896ab07d1691c7248e2f22c19b17da49c71271afe7398de72790302366fe72

Tx prefix hash: 5d28d486327baecc36cc46195b763b55ce700193fa4c69f9e64b8b058b5e46c5
Tx public key: fad0ad35bc369c17a59761f815f064a08667a0d1a4f4744940f0c06e7d9afbb5
Timestamp: 1712606259 Timestamp [UCT]: 2024-04-08 19:57:39 Age [y:d:h:m:s]: 01:214:11:25:12
Block: 996228 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 411979 RingCT/type: yes/0
Extra: 01fad0ad35bc369c17a59761f815f064a08667a0d1a4f4744940f0c06e7d9afbb502110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: abd6ac19c798a024db1e49b6759f7a01037de36131c9b2f4c8ec6fd5d146c32c 0.600000000000 1456644 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": 996238, "vin": [ { "gen": { "height": 996228 } } ], "vout": [ { "amount": 600000000, "target": { "key": "abd6ac19c798a024db1e49b6759f7a01037de36131c9b2f4c8ec6fd5d146c32c" } } ], "extra": [ 1, 250, 208, 173, 53, 188, 54, 156, 23, 165, 151, 97, 248, 21, 240, 100, 160, 134, 103, 160, 209, 164, 244, 116, 73, 64, 240, 192, 110, 125, 154, 251, 181, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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