Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f25042c39fb2f4a48ede68b565b7117de26112a3165e182c00abbedfe8a7d5f

Tx prefix hash: 862a90a22030d517aba410feeb1952d8d0226dd80ab8274773e61c835bcfa4be
Tx public key: f36d376ebcbfdf0dca5d6c9d9f91859c3a901b89b565f539ebd1a8bbb6be428d
Timestamp: 1699656272 Timestamp [UCT]: 2023-11-10 22:44:32 Age [y:d:h:m:s]: 01:143:04:25:35
Block: 888895 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 363506 RingCT/type: yes/0
Extra: 01f36d376ebcbfdf0dca5d6c9d9f91859c3a901b89b565f539ebd1a8bbb6be428d02110000000afaf35c9c000000000000000000

1 output(s) for total of 0.696180520000 dcy

stealth address amount amount idx
00: cf0b3c61d308b35c21d7a9b5959e93f0e3c7f8e11be469bf7d1e07f76a9405b5 0.696180520000 1344862 of 0

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": 888905, "vin": [ { "gen": { "height": 888895 } } ], "vout": [ { "amount": 696180520, "target": { "key": "cf0b3c61d308b35c21d7a9b5959e93f0e3c7f8e11be469bf7d1e07f76a9405b5" } } ], "extra": [ 1, 243, 109, 55, 110, 188, 191, 223, 13, 202, 93, 108, 157, 159, 145, 133, 156, 58, 144, 27, 137, 181, 101, 245, 57, 235, 209, 168, 187, 182, 190, 66, 141, 2, 17, 0, 0, 0, 10, 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