Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd10025bfa17561d06341c8868371e9c8935f1108764067e51486a507bac7789

Tx prefix hash: 5af6b30051958fd6211227093458aa5618dcce62426e5c267da0536e042ed54a
Tx public key: 4d07aa1131d0bc511c8c83ffd29f276c097604e7a76fccfc553911ca987c9530
Timestamp: 1578458114 Timestamp [UTC]: 2020-01-08 04:35:14 Age [y:d:h:m:s]: 06:242:00:53:15
Block: 40965 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1587564 RingCT/type: yes/0
Extra: 014d07aa1131d0bc511c8c83ffd29f276c097604e7a76fccfc553911ca987c953002112053b5a800000000000000000000000000

1 output(s) for total of 0.449028897949 xmr

stealth address amount amount idx tag
00: e3492566a73c5c0f1ef5231a6e970022cefdfa0ebfd8faf5d7784fdb37ac983e 0.449028897949 72512 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": 40975, "vin": [ { "gen": { "height": 40965 } } ], "vout": [ { "amount": 449028897949, "target": { "key": "e3492566a73c5c0f1ef5231a6e970022cefdfa0ebfd8faf5d7784fdb37ac983e" } } ], "extra": [ 1, 77, 7, 170, 17, 49, 208, 188, 81, 28, 140, 131, 255, 210, 159, 39, 108, 9, 118, 4, 231, 167, 111, 204, 252, 85, 57, 17, 202, 152, 124, 149, 48, 2, 17, 32, 83, 181, 168, 0, 0, 0, 0, 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: