Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b8d73c30b5991f96dcfc6300eac8abb60f4d9da2d0e8d9a3ffef4e508bfbfb6

Tx prefix hash: bf0601ea649d248ada5fa641ec5a89b4a81dd302a2b1f845e7d94ddfa95e1a59
Tx public key: 6a82de6d98fd45391cccc659c96a95a746d7a41b7855d2b0b60e673271e25390
Timestamp: 1756977646 Timestamp [UTC]: 2025-09-04 09:20:46 Age [y:d:h:m:s]: 00:259:16:55:17
Block: 1361082 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 179063 RingCT/type: yes/0
Extra: 016a82de6d98fd45391cccc659c96a95a746d7a41b7855d2b0b60e673271e25390021100000001b2f784c4000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 6f3f69ba5dafc553ce39f13fb06d20b96c4d54a439bf8d351515aa6e9846a49a 0.000600000000 1849095 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": 1361092, "vin": [ { "gen": { "height": 1361082 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6f3f69ba5dafc553ce39f13fb06d20b96c4d54a439bf8d351515aa6e9846a49a" } } ], "extra": [ 1, 106, 130, 222, 109, 152, 253, 69, 57, 28, 204, 198, 89, 201, 106, 149, 167, 70, 215, 164, 27, 120, 85, 210, 176, 182, 14, 103, 50, 113, 226, 83, 144, 2, 17, 0, 0, 0, 1, 178, 247, 132, 196, 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: