Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c991d8d972c5d0a2bc14a98891ca22fbd3454af9ed0261b69ff0e5854fc4db69

Tx prefix hash: 8587c6bc73775cab18d147f37ef21eef4dfaee17710b0de322f52bfe7941c315
Tx public key: e03a4616ac56ddcff8bf13cd733373abb2910f07ea78b233b3a915457ed4d3ef
Timestamp: 1648921313 Timestamp [UTC]: 2022-04-02 17:41:53 Age [y:d:h:m:s]: 04:232:04:35:43
Block: 471784 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1210420 RingCT/type: yes/0
Extra: 01e03a4616ac56ddcff8bf13cd733373abb2910f07ea78b233b3a915457ed4d3ef0211000000014da16a3a000000000000000000

1 output(s) for total of 0.016779692894 xmr

stealth address amount amount idx tag
00: 6bff1b959751a48d2084455e1b417202abb7d95dda33cf4488eb8153545bb259 0.016779692894 891192 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": 471794, "vin": [ { "gen": { "height": 471784 } } ], "vout": [ { "amount": 16779692894, "target": { "key": "6bff1b959751a48d2084455e1b417202abb7d95dda33cf4488eb8153545bb259" } } ], "extra": [ 1, 224, 58, 70, 22, 172, 86, 221, 207, 248, 191, 19, 205, 115, 51, 115, 171, 178, 145, 15, 7, 234, 120, 178, 51, 179, 169, 21, 69, 126, 212, 211, 239, 2, 17, 0, 0, 0, 1, 77, 161, 106, 58, 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: