Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e8afaf72dca67040abb633c6d7834e68d76a1e2fa156820dc79125191ea9cb5c

Tx prefix hash: 42905414aca6f210c99b37f1ac1602b32609121aff981b1c2e31fa183d038d42
Tx public key: e1a5ca10d4216b8d6c227691d3bb40d997932f95401e9d8012da480769ee6c81
Timestamp: 1657716028 Timestamp [UCT]: 2022-07-13 12:40:28 Age [y:d:h:m:s]: 02:302:17:30:37
Block: 542885 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 737516 RingCT/type: yes/0
Extra: 01e1a5ca10d4216b8d6c227691d3bb40d997932f95401e9d8012da480769ee6c8102110000000175e3f0e9000000000000000000

1 output(s) for total of 9.754314979000 dcy

stealth address amount amount idx
00: bbc3739d14c821969fd9d0eff8669b4951c15a3775b24f39963b75cee1021671 9.754314979000 973494 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": 542895, "vin": [ { "gen": { "height": 542885 } } ], "vout": [ { "amount": 9754314979, "target": { "key": "bbc3739d14c821969fd9d0eff8669b4951c15a3775b24f39963b75cee1021671" } } ], "extra": [ 1, 225, 165, 202, 16, 212, 33, 107, 141, 108, 34, 118, 145, 211, 187, 64, 217, 151, 147, 47, 149, 64, 30, 157, 128, 18, 218, 72, 7, 105, 238, 108, 129, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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