Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc7cba97ec6a5495d10cef760cc05037838f8b022d6ac4616f2da2ced6ed295d

Tx prefix hash: d0593fba1be9124d80d49b7eeb50e87c7a9ac275368c2cfb923e1a12599c0e4d
Tx public key: 42f9e9eca9d8fe364a0e449675b0d4aeeeea2fc5c1c39e7911b9f10487af6e55
Timestamp: 1580886633 Timestamp [UTC]: 2020-02-05 07:10:33 Age [y:d:h:m:s]: 06:288:05:04:52
Block: 58897 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1622223 RingCT/type: yes/0
Extra: 0142f9e9eca9d8fe364a0e449675b0d4aeeeea2fc5c1c39e7911b9f10487af6e5502110000000149b77a3d000000000000000000

1 output(s) for total of 0.391607147337 xmr

stealth address amount amount idx tag
00: 293463dbfee659c08c165ddbdc2d1ae586385e76cf224bf3c10413f2b53ccd2a 0.391607147337 108833 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": 58907, "vin": [ { "gen": { "height": 58897 } } ], "vout": [ { "amount": 391607147337, "target": { "key": "293463dbfee659c08c165ddbdc2d1ae586385e76cf224bf3c10413f2b53ccd2a" } } ], "extra": [ 1, 66, 249, 233, 236, 169, 216, 254, 54, 74, 14, 68, 150, 117, 176, 212, 174, 238, 234, 47, 197, 193, 195, 158, 121, 17, 185, 241, 4, 135, 175, 110, 85, 2, 17, 0, 0, 0, 1, 73, 183, 122, 61, 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: