Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae5cffbcbe7935370e4943b8ad5d1484efe90024ccd39e16c4a77afbeea8a527

Tx prefix hash: fcee1b3c1dfffb3e9175f37a0e02096dedebeec48836cb748696b2a71185b1f9
Tx public key: fb4acb7b6140f0dbe1ea37cdfb68edef0784a73551cfda4a997f00c6abcd8593
Timestamp: 1646235226 Timestamp [UTC]: 2022-03-02 15:33:46 Age [y:d:h:m:s]: 04:075:23:22:13
Block: 449854 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1085316 RingCT/type: yes/0
Extra: 01fb4acb7b6140f0dbe1ea37cdfb68edef0784a73551cfda4a997f00c6abcd85930211000000064da16a3a000000000000000000

1 output(s) for total of 0.019835686408 xmr

stealth address amount amount idx tag
00: b3b16bbce21e22744ef0fdad5c79904db953cc25b41455583d841fcf53fd3e1a 0.019835686408 864591 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": 449864, "vin": [ { "gen": { "height": 449854 } } ], "vout": [ { "amount": 19835686408, "target": { "key": "b3b16bbce21e22744ef0fdad5c79904db953cc25b41455583d841fcf53fd3e1a" } } ], "extra": [ 1, 251, 74, 203, 123, 97, 64, 240, 219, 225, 234, 55, 205, 251, 104, 237, 239, 7, 132, 167, 53, 81, 207, 218, 74, 153, 127, 0, 198, 171, 205, 133, 147, 2, 17, 0, 0, 0, 6, 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: