Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 87aa84ca23c7a6a47eb173d3cd92d01296a794fa96aa6183fee1fd3edd408863

Tx prefix hash: b374adedead2c313df0e0444750412563d5a5b71e0a4954d620a7149e88ccd16
Tx public key: 9a6e7e0858f01d183396ef535ae688f24ef0a0e79b0b6fc2049a894ecd0fdc1f
Timestamp: 1743563946 Timestamp [UTC]: 2025-04-02 03:19:06 Age [y:d:h:m:s]: 01:233:14:41:20
Block: 1252407 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 431087 RingCT/type: yes/0
Extra: 019a6e7e0858f01d183396ef535ae688f24ef0a0e79b0b6fc2049a894ecd0fdc1f0211000000094060f6d2000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: fdfa8f89e84788907a9ff799667a76fb07f93daaf4d5e6222dc44ace5a1a2e5c 0.000600000000 1739488 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": 1252417, "vin": [ { "gen": { "height": 1252407 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fdfa8f89e84788907a9ff799667a76fb07f93daaf4d5e6222dc44ace5a1a2e5c" } } ], "extra": [ 1, 154, 110, 126, 8, 88, 240, 29, 24, 51, 150, 239, 83, 90, 230, 136, 242, 78, 240, 160, 231, 155, 11, 111, 194, 4, 154, 137, 78, 205, 15, 220, 31, 2, 17, 0, 0, 0, 9, 64, 96, 246, 210, 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: