Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4c95a30f6c319c7b55929fd0991c51639758be321e3b751e41145580ec5b30c

Tx prefix hash: 3aecbdeec16fc81e8579a22429babfe05307a955c1d6c32634061941990c7e54
Tx public key: 5df22bcd45b5a73707eeeb6a381c50cfa0ee68946f7444891012d7f377a2eaec
Timestamp: 1701162174 Timestamp [UCT]: 2023-11-28 09:02:54 Age [y:d:h:m:s]: 01:200:13:48:59
Block: 901378 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 404457 RingCT/type: yes/0
Extra: 015df22bcd45b5a73707eeeb6a381c50cfa0ee68946f7444891012d7f377a2eaec02110000000975e3f0e9000000000000000000

1 output(s) for total of 0.632937005000 dcy

stealth address amount amount idx
00: 493521881e4a74dbc1408fb4634b693f6a515610ca13f2a50999c7aaf87fc4c6 0.632937005000 1357937 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": 901388, "vin": [ { "gen": { "height": 901378 } } ], "vout": [ { "amount": 632937005, "target": { "key": "493521881e4a74dbc1408fb4634b693f6a515610ca13f2a50999c7aaf87fc4c6" } } ], "extra": [ 1, 93, 242, 43, 205, 69, 181, 167, 55, 7, 238, 235, 106, 56, 28, 80, 207, 160, 238, 104, 148, 111, 116, 68, 137, 16, 18, 215, 243, 119, 162, 234, 236, 2, 17, 0, 0, 0, 9, 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