Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41f495394adbc16b4455c93da2b7faedad63bcfbf75318c5b5edb9b67a8509dd

Tx prefix hash: 8c410d178ae066032d5430316d12c7ed03ed761c7f118370735c206b85814a56
Tx public key: 774d73697edcd7113f1a8b1216eb7feee0197f6b00f622a196fa3aa80dd14289
Timestamp: 1712691863 Timestamp [UTC]: 2024-04-09 19:44:23 Age [y:d:h:m:s]: 02:037:21:51:38
Block: 996946 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 539096 RingCT/type: yes/0
Extra: 01774d73697edcd7113f1a8b1216eb7feee0197f6b00f622a196fa3aa80dd1428902110000000459dad3f5000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a7881ec88544caeda90db4c3abbdf7c2d512a40d5e3297839cbb1e5bd3c4089a 0.000600000000 1457374 of 15 -

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": 996956, "vin": [ { "gen": { "height": 996946 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a7881ec88544caeda90db4c3abbdf7c2d512a40d5e3297839cbb1e5bd3c4089a" } } ], "extra": [ 1, 119, 77, 115, 105, 126, 220, 215, 17, 63, 26, 139, 18, 22, 235, 127, 238, 224, 25, 127, 107, 0, 246, 34, 161, 150, 250, 58, 168, 13, 209, 66, 137, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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: