Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c72fe9b669d173c27d13d81c7032026727a6fb51665e855ba8fd42e7a39ff413

Tx prefix hash: bbf85d7f60c7b545f221ac406bc748ddebad7b159a097f9862e7ccaddf28f89e
Tx public key: 2b68c5fd390bcca7135aeb39e6bbec76f48ed5d9fcc63aa234a96a259052b94d
Timestamp: 1578373587 Timestamp [UTC]: 2020-01-07 05:06:27 Age [y:d:h:m:s]: 06:125:14:28:40
Block: 40286 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1491016 RingCT/type: yes/0
Extra: 012b68c5fd390bcca7135aeb39e6bbec76f48ed5d9fcc63aa234a96a259052b94d0211000000c4b221b3d1000000000000000000

1 output(s) for total of 0.451353282972 xmr

stealth address amount amount idx tag
00: bb2e1f77d47b678c2f1a7b82863ac1de267d949f8745d5b8cc31fd52d0759770 0.451353282972 70550 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 dinastycoin-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": 40296, "vin": [ { "gen": { "height": 40286 } } ], "vout": [ { "amount": 451353282972, "target": { "key": "bb2e1f77d47b678c2f1a7b82863ac1de267d949f8745d5b8cc31fd52d0759770" } } ], "extra": [ 1, 43, 104, 197, 253, 57, 11, 204, 167, 19, 90, 235, 57, 230, 187, 236, 118, 244, 142, 213, 217, 252, 198, 58, 162, 52, 169, 106, 37, 144, 82, 185, 77, 2, 17, 0, 0, 0, 196, 178, 33, 179, 209, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: