Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b1b69ca5a9fbc32b02a34500e294f84646cf5cc120a58b16c51c9e2c9e5cf90

Tx prefix hash: f4f5fd8a22fcd802ab3a65d7bfd86725d7051abeb23dcfdae86d8425805c7f6c
Tx public key: 2812d1427bde5f6d44ec53e1bde3787f1079db9509a1adef5d14bf5d220109f1
Timestamp: 1645257299 Timestamp [UTC]: 2022-02-19 07:54:59 Age [y:d:h:m:s]: 04:277:07:37:45
Block: 441773 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1241721 RingCT/type: yes/0
Extra: 012812d1427bde5f6d44ec53e1bde3787f1079db9509a1adef5d14bf5d220109f102110000000106faf294000000000000000000

1 output(s) for total of 0.021097109312 xmr

stealth address amount amount idx tag
00: e3d51efcb055273270a348adbca1c3720a315e8ff20d9dccb869c11437f224bb 0.021097109312 854406 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": 441783, "vin": [ { "gen": { "height": 441773 } } ], "vout": [ { "amount": 21097109312, "target": { "key": "e3d51efcb055273270a348adbca1c3720a315e8ff20d9dccb869c11437f224bb" } } ], "extra": [ 1, 40, 18, 209, 66, 123, 222, 95, 109, 68, 236, 83, 225, 189, 227, 120, 127, 16, 121, 219, 149, 9, 161, 173, 239, 93, 20, 191, 93, 34, 1, 9, 241, 2, 17, 0, 0, 0, 1, 6, 250, 242, 148, 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: