Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fef520850ff49997e113d939661b1f3d35d022104f27fae4148b3679b4ea9169

Tx prefix hash: 099a0398427d7b3f6fa042ad167cd5771c9a49ade996cecb471359ffa4714385
Tx public key: 4e33d075213cc7da4344384514e53b7ef4999e821a8a9e155c0dd43b09e7e4b7
Timestamp: 1577978074 Timestamp [UCT]: 2020-01-02 15:14:34 Age [y:d:h:m:s]: 04:357:14:16:32
Block: 37300 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1144650 RingCT/type: yes/0
Extra: 014e33d075213cc7da4344384514e53b7ef4999e821a8a9e155c0dd43b09e7e4b70211000000108a2ee0d9000000000000000000

1 output(s) for total of 461.753788807000 dcy

stealth address amount amount idx
00: a3b5fa5fa14be4a31e82644fa6bc9eece1fa0d1ad249486e8c613bb0732b56ea 461.753788807000 63268 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": 37310, "vin": [ { "gen": { "height": 37300 } } ], "vout": [ { "amount": 461753788807, "target": { "key": "a3b5fa5fa14be4a31e82644fa6bc9eece1fa0d1ad249486e8c613bb0732b56ea" } } ], "extra": [ 1, 78, 51, 208, 117, 33, 60, 199, 218, 67, 68, 56, 69, 20, 229, 59, 126, 244, 153, 158, 130, 26, 138, 158, 21, 92, 13, 212, 59, 9, 231, 228, 183, 2, 17, 0, 0, 0, 16, 138, 46, 224, 217, 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