Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 229f70957eb4ffb2de0a78aed66506c0d417a5a72356f05af4ebb5e3d7555a08

Tx prefix hash: 76cd849a8cea18fbdb4d4a4e277af86d6d16af01a3baa9b5e50853e1a731527e
Tx public key: 97769255507cb4470de875476e1ccd03319b16a3ff5b643ebf4ab0e09980b24c
Timestamp: 1617929042 Timestamp [UTC]: 2021-04-09 00:44:02 Age [y:d:h:m:s]: 05:228:09:37:09
Block: 235750 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1447744 RingCT/type: yes/0
Extra: 0197769255507cb4470de875476e1ccd03319b16a3ff5b643ebf4ab0e09980b24c0211000000116eb9c26a000000000000000000

1 output(s) for total of 0.101592806693 xmr

stealth address amount amount idx tag
00: 346dde05a0ea0907f1e482032abcd610d90513f3da1b28fdfbb36d32260e6138 0.101592806693 489900 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": 235760, "vin": [ { "gen": { "height": 235750 } } ], "vout": [ { "amount": 101592806693, "target": { "key": "346dde05a0ea0907f1e482032abcd610d90513f3da1b28fdfbb36d32260e6138" } } ], "extra": [ 1, 151, 118, 146, 85, 80, 124, 180, 71, 13, 232, 117, 71, 110, 28, 205, 3, 49, 155, 22, 163, 255, 91, 100, 62, 191, 74, 176, 224, 153, 128, 178, 76, 2, 17, 0, 0, 0, 17, 110, 185, 194, 106, 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: