Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c738b6b6fcfa7b173f567c6fb25f9e39eec5d3b68095c6042cf4feb41225d447

Tx prefix hash: 1cbed020023285886861fb51c9360393eb9142e1fefa5e8a10f482a3cb7c707e
Tx public key: 39653ea49d734e82af741cbaa700abb4be8f2579dbc8d09d9ca3effe8e2e728d
Timestamp: 1633737427 Timestamp [UTC]: 2021-10-08 23:57:07 Age [y:d:h:m:s]: 04:221:07:25:35
Block: 349459 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1186245 RingCT/type: yes/0
Extra: 0139653ea49d734e82af741cbaa700abb4be8f2579dbc8d09d9ca3effe8e2e728d0211000000113fc41461000000000000000000

1 output(s) for total of 0.042667548360 xmr

stealth address amount amount idx tag
00: 77847b5b2a7c85ffd3a3e118c730801eacb044b9bc1a60df3f054106efa0aeb6 0.042667548360 715456 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": 349469, "vin": [ { "gen": { "height": 349459 } } ], "vout": [ { "amount": 42667548360, "target": { "key": "77847b5b2a7c85ffd3a3e118c730801eacb044b9bc1a60df3f054106efa0aeb6" } } ], "extra": [ 1, 57, 101, 62, 164, 157, 115, 78, 130, 175, 116, 28, 186, 167, 0, 171, 180, 190, 143, 37, 121, 219, 200, 208, 157, 156, 163, 239, 254, 142, 46, 114, 141, 2, 17, 0, 0, 0, 17, 63, 196, 20, 97, 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: