Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b737dc8cae527deb4aec43d5a71a153b2ba93918ad306cfe2b2853da2b68ab42

Tx prefix hash: d8069c6f0b07647b3015e8bdae3ca05f43b7d865891fbe56174c902bea2220e9
Tx public key: a4f50f3ed307ae4e16f0b066933a144e87620700d3a18c1bf2cba9796248d1d6
Timestamp: 1638222887 Timestamp [UCT]: 2021-11-29 21:54:47 Age [y:d:h:m:s]: 03:069:23:54:26
Block: 384944 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 828695 RingCT/type: yes/0
Extra: 01a4f50f3ed307ae4e16f0b066933a144e87620700d3a18c1bf2cba9796248d1d6021100000002e59f5d07000000000000000000

1 output(s) for total of 32.550309901000 dcy

stealth address amount amount idx
00: 1f8b15ca5705b337db567b0be0dbde5fe2aa4c620e80e52a3ce54882f09c07df 32.550309901000 776887 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": 384954, "vin": [ { "gen": { "height": 384944 } } ], "vout": [ { "amount": 32550309901, "target": { "key": "1f8b15ca5705b337db567b0be0dbde5fe2aa4c620e80e52a3ce54882f09c07df" } } ], "extra": [ 1, 164, 245, 15, 62, 211, 7, 174, 78, 22, 240, 176, 102, 147, 58, 20, 78, 135, 98, 7, 0, 211, 161, 140, 27, 242, 203, 169, 121, 98, 72, 209, 214, 2, 17, 0, 0, 0, 2, 229, 159, 93, 7, 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