Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe3d17731d656d67dcbf61e5b994881851d2e1707985131a050d5a53218170c7

Tx prefix hash: f405d8c033c52eeeab50b0a8ee3ea32f5568bb9256bd5f7bd24a6e816b963144
Tx public key: c18eb13c988b48158c4e3459e5a33e9e638a91b654756f04bc205b03d9020ca0
Timestamp: 1716662006 Timestamp [UTC]: 2024-05-25 18:33:26 Age [y:d:h:m:s]: 02:177:06:31:27
Block: 1029890 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 651634 RingCT/type: yes/0
Extra: 01c18eb13c988b48158c4e3459e5a33e9e638a91b654756f04bc205b03d9020ca002110000000952d47e94000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 16a29727ed6a95bd68fdbba71b57a9142bc00ef8c007a2130d52b74b4b2a89c2 0.000600000000 1498101 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": 1029900, "vin": [ { "gen": { "height": 1029890 } } ], "vout": [ { "amount": 600000000, "target": { "key": "16a29727ed6a95bd68fdbba71b57a9142bc00ef8c007a2130d52b74b4b2a89c2" } } ], "extra": [ 1, 193, 142, 177, 60, 152, 139, 72, 21, 140, 78, 52, 89, 229, 163, 62, 158, 99, 138, 145, 182, 84, 117, 111, 4, 188, 32, 91, 3, 217, 2, 12, 160, 2, 17, 0, 0, 0, 9, 82, 212, 126, 148, 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: