Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f4b19ae5d0501c58c3daa8f47de7bb12cf5792494103e5e369979d181ca141f

Tx prefix hash: 3d06c97fd838a284757c91366b1aa12c71af1395b749d0636424a8e10c9d9210
Tx public key: 642f197d3b13a01cdf921c31244c304ff707df85fe84bc803d95c3d0e5d2decd
Timestamp: 1580264865 Timestamp [UTC]: 2020-01-29 02:27:45 Age [y:d:h:m:s]: 06:104:17:54:36
Block: 54431 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1477107 RingCT/type: yes/0
Extra: 01642f197d3b13a01cdf921c31244c304ff707df85fe84bc803d95c3d0e5d2decd02110000000149b77a3d000000000000000000

1 output(s) for total of 0.405180306015 xmr

stealth address amount amount idx tag
00: fe3f3d2300adb98847e6b0a226952885947b9667e9a1e2ddf564972900ae5074 0.405180306015 100819 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": 54441, "vin": [ { "gen": { "height": 54431 } } ], "vout": [ { "amount": 405180306015, "target": { "key": "fe3f3d2300adb98847e6b0a226952885947b9667e9a1e2ddf564972900ae5074" } } ], "extra": [ 1, 100, 47, 25, 125, 59, 19, 160, 28, 223, 146, 28, 49, 36, 76, 48, 79, 247, 7, 223, 133, 254, 132, 188, 128, 61, 149, 195, 208, 229, 210, 222, 205, 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: