Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d7bc2076feabf2a2bef74b4c694f41581db1186371b83c4b7ed3a78d8f31c3f

Tx prefix hash: 9d2b32b6f9eeb5e763cc563ebe1f436fe23ea056f9b12ce0a7609f763ecb4e11
Tx public key: 6e8dc838e027a311692a43a51946363012c42121c37fb12441a1b4d21068c1a1
Timestamp: 1739176270 Timestamp [UTC]: 2025-02-10 08:31:10 Age [y:d:h:m:s]: 01:093:06:10:51
Block: 1216100 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317575 RingCT/type: yes/0
Extra: 016e8dc838e027a311692a43a51946363012c42121c37fb12441a1b4d21068c1a10211000000021f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 34e95a0ee1a5e740a1d0070fca23e6484fb41958a71c218afcb017ef8b853b70 0.000600000000 1702901 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": 1216110, "vin": [ { "gen": { "height": 1216100 } } ], "vout": [ { "amount": 600000000, "target": { "key": "34e95a0ee1a5e740a1d0070fca23e6484fb41958a71c218afcb017ef8b853b70" } } ], "extra": [ 1, 110, 141, 200, 56, 224, 39, 163, 17, 105, 42, 67, 165, 25, 70, 54, 48, 18, 196, 33, 33, 195, 127, 177, 36, 65, 161, 180, 210, 16, 104, 193, 161, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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: