Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2187f41774d5f5d267da5ff0e26ed35def7334736746111ca5fc77e9113c3979

Tx prefix hash: ff6030a355e7b32f325a3ded2cd1c9d2e3452c22555ef8db8aba2d4d68fa9ada
Tx public key: 0551468f1145116a3c3ac9fed14dc51d73f39418c098a58a7ab39c18eba58c98
Timestamp: 1769680906 Timestamp [UTC]: 2026-01-29 10:01:46 Age [y:d:h:m:s]: 00:296:22:16:29
Block: 1466114 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217380 RingCT/type: yes/0
Extra: 010551468f1145116a3c3ac9fed14dc51d73f39418c098a58a7ab39c18eba58c98021100000001215bbf89000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a3f33774645e0ac2ac7f1dcf163ceac95cb9c34c485dd69dacff59b5c8b432fa 0.000600000000 1955346 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": 1466124, "vin": [ { "gen": { "height": 1466114 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a3f33774645e0ac2ac7f1dcf163ceac95cb9c34c485dd69dacff59b5c8b432fa" } } ], "extra": [ 1, 5, 81, 70, 143, 17, 69, 17, 106, 60, 58, 201, 254, 209, 77, 197, 29, 115, 243, 148, 24, 192, 152, 165, 138, 122, 179, 156, 24, 235, 165, 140, 152, 2, 17, 0, 0, 0, 1, 33, 91, 191, 137, 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: